|
|
| Author |
Thread Statistics | Show CCP posts - 16 post(s) |
War Fairy
Cascading Failure
Un.Bound
3
   |
Posted - 2014.05.06 17:40:00 -
[1] - Quote
I support this change. |
War Fairy
Cascading Failure
Un.Bound
3
|
Posted - 2014.05.06 17:43:00 -
[2] - Quote
Valterra Craven wrote:Querns wrote:Valterra Craven wrote:CCP FoxFour wrote:
This is data that is available via the API but not in the client in any way.
How many examples of data being available in the API exist and why aren't you fixing all of them at the same time? CCP FoxFour wrote:
That is the core reason for this change, there are some other smaller ones but that is the big one. We are of course open to discussing how this information should be available in the client and how we reconcile that available knowledge with the goal that wormhole space should be mysterious and unknown. If this brought into the client we would of course be willing to bring it back to the API as well.
You should not remove something from the API without first deciding if it will be available in the client in the future. Decided that first, and then decide how to handle the API. Not before. Also, you have a strange way of iterating on things if all you are going to do is constantly remove features WH people use all the time. Ah, yes, this argument again -- all changes must be delayed until every single niggling discrepancy even tangentially related to the proposed change are also handled. How many times must we see this demonstrably incorrect thinking before it gets relegated to the garbage can where it belongs? I'm not saying it should be delayed until all descrepencies are handled. I'm saying it should be delayed until game design makes their choice. What I am saying is that since they are now enforcing a rule that wasn't previously that it should be enforced EVENLY and research should be undertaken to ensure that is the case.
As stated by the DEVs in the other thread the API goes against the original design and they had the designers sign off on it before they announced it. |
War Fairy
Cascading Failure
Un.Bound
3
|
Posted - 2014.05.06 17:46:00 -
[3] - Quote
Cue Who wrote:The only thing this change does is make it easier to PvE. EVE has always maintained a balance between risk and reward, with WHs being the best ISK in the game, why are you decreasing risk? As it stands, it's too safe in W-Space already, now it's going to be even safer? As it stands, WHs are dead empty. There's a limited number of people who want to live in wormholes. Removing the ability to tell when a wormhole is active will make them even more empty.
Trivial use of D-Scan will show if a worm hole is active.
All this prevents is automated notification that a WH has PvE activity within the last hour.
|
War Fairy
Cascading Failure
Un.Bound
4
|
Posted - 2014.05.06 17:47:00 -
[4] - Quote
Aryth wrote: Arguments to delay it pending a game design decision though I think have a lot of validity.
Done https://forums.eveonline.com/default.aspx?g=posts&m=4558494#post4558494
|
War Fairy
Cascading Failure
Un.Bound
4
|
Posted - 2014.05.06 18:46:00 -
[5] - Quote
Necharo Rackham wrote:Querns wrote:
It is the issue; we are talking about the information exposed via the API. Capital geography information is exposed via the SDE. These are two different things.
Feel free to provide another example of information exposed via the API that is not available in the client.
Well, if we are going for an appeal to mystery and (implicitly) lore, then the SDE has no place in the game either.
Lore never drives change. Only game design drives change. Lore is at best a fun story that is made up about the change.
|
War Fairy
Cascading Failure
Un.Bound
4
|
Posted - 2014.05.06 18:48:00 -
[6] - Quote
Domanique Altares wrote:
Would you continue to preemptively remove it from the API due to the fact that you dislike its presentation in an out-of-game tool, owed solely to the failure on CCP's part to provide an in-game one?
This is incorrect. CCP did not fail to provide an in-game one. They chose not to by design.
To explain a different way. The exposure via API is the mistake. The client not showing it is correct.
|
War Fairy
Cascading Failure
Un.Bound
4
|
Posted - 2014.05.06 19:55:00 -
[7] - Quote
Vincent Athena wrote:CCP FoxFour wrote:...
The reason we're proposing this change: This is data that is available via the API but not in the client in any way.
.
.
.
Yes, it is. Park a cloaked alt by every site in a W-system and take data. Warp about as needed. Yes, it is a very hard way to get the data from the client, but it is a way. Thus your statement "This is data that is available via the API but not in the client in any way" is wrong. There is a way, a very cumbersome way, but there is a way.
That's info from player not client.
|
War Fairy
Cascading Failure
Un.Bound
4
|
Posted - 2014.05.06 20:01:00 -
[8] - Quote
Blodhgarm Dethahal wrote:Better make this so in K-Space as well... that information is not publicly available in client either you know...
If you go through with it of course...
Yes it is. It's in the map. |
|
|
| |
|